Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix errors in viewer caused by WsValidation and new Update Api #1288

Merged
merged 2 commits into from
Nov 28, 2024

Conversation

hahn-kev
Copy link
Collaborator

WsId validation broke the LfClassic api as it was using the wsId '__key' to passing some ids across.

Additionally now that we're using the new update api we are just always calling api.UpdateEntry instead of only calling it when changes are detected via json patch, this meant that the Viewer was calling update even when it's not implemented which was throwing an error

Copy link

UI unit Tests

12 tests  ±0   12 ✅ ±0   0s ⏱️ ±0s
 4 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit ffb7b13. ± Comparison against base commit e32f341.

Copy link

C# Unit Tests

98 tests  ±0   98 ✅ ±0   5s ⏱️ ±0s
15 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit ffb7b13. ± Comparison against base commit e32f341.

Copy link
Contributor

@myieye myieye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for noticing that!

I should have checked the viewer in prod!
The viewer tests are currently broken in staging, due to languageforge not being migrated to the new cluster, so I just ignored their failures. Woops.

@myieye myieye merged commit ada6d56 into develop Nov 28, 2024
22 checks passed
@myieye myieye deleted the chore/fix-viewer branch November 28, 2024 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants